Apparatus, systems and methods for customer specific receipt advertising

ABSTRACT

The present invention (sometimes referred to herein as Customer Specific Receipt Advertising (“CSRA”)) will provide apparatus, systems and methods that will provide participating retailers and service providers the ability to offer coupons, advertising and communications on printed or electronic receipts such that the coupons are specifically oriented towards the customer&#39;s buying habits and needs. Customers can choose to be included, or not to be included, in this program when establishing their account with Immtec&#39;s mewallet™ system, or any credit or debit card provider. The customer can also sign up for this service with any participating, licensed merchant.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional PatentApplication Ser. No. 60/234,623 (“Apparatus, Systems and Methods forCustomer Specific Receipt Advertising”) filed Sep. 22, 2000, and No.60/255,981 (“Apparatus, Systems and Methods for Customer SpecificReceipt Advertising”) filed Dec. 15, 2000, the disclosures of which areincorporated herein in full for all purposes as if fully stated here.The disclosures of U.S. Provisional Patent Application Ser. No.60/181,600 filed Feb. 10, 2000, No. 60/187,924, filed Mar. 8, 2000, No.60/255,980, filed Dec. 15, 2000, and Int'l. Application No.PCT/US01/04258, Int'l Filing Date Feb. 9, 2001 are incorporated hereinin full for all purposes as if fully stated here.

SUMMARY OF THE INVENTION

[0002] The present invention (sometimes referred to herein as CustomerSpecific Receipt Advertising (“CSRA”)) will provide apparatus, systemsand methods that will provide participating retailers and serviceproviders the ability to offer coupons, advertising, promotional offers,and communications on printed or electronic receipts such that thecoupons are specifically oriented towards each particular customer'sbuying habits, preferences and needs. At the same time, in the exemplaryembodiment of the invention, each customer's buying habits, preferencesand needs could be kept confidential from the knowledge of individualvendors.

[0003] With the present invention, Customers would be able to choose tobe included, or not to be included, in this program when establishingtheir account with Immtec's mewallet™ system, or other CSRA-enabledcredit or debit card provider. The customer could also sign up for thisservice with any participating, licensed merchant.

[0004] Consumer data would be kept on secure Immtec servers. The CSRAback-end software would reside on the Immtec servers as well. CSRAinterface software could be licensed to retailers, organizations, banks,manufacturers, wholesalers, advertising companies, marketing companiesand credit/debit card providers. CSRA data would not be sold to otherproviders under any circumstances.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] These and other features of the present invention are more fullyset forth in the following description of exemplary embodiments of theinvention. The description is presented with reference to theaccompanying drawings in which:

[0006]FIG. 1 is a high level flow diagram depicting a customer sign-upprocedure in an exemplary embodiment of the present invention;

[0007]FIG. 2 is a high level flow diagram depicting an Internet-basedprocedure for a customer to change customer use preferences in anexemplary embodiment of the present invention;

[0008]FIG. 3 is a high level flow diagram depicting a telephone-basedprocedure for a customer to change customer use preferences in anexemplary embodiment of the present invention;

[0009] FIGS. 4-6 provide a high level flow diagram depicting anauthorized-service-center-based procedure for a customer to changecustomer use preferences in an exemplary embodiment of the presentinvention;

[0010] FIGS. 7-8 provide a high level flow diagram depicting customerspecific receipt advertising processing functions in an exemplaryembodiment of the present invention;

[0011]FIG. 9 is a high level flow diagram depicting an Internet-basedvendor log-in interface in an exemplary embodiment of the presentinvention;

[0012]FIG. 10 is a high level flow diagram depicting an Internet-basedvendor new offer upload process in an exemplary embodiment of thepresent invention;

[0013]FIG. 11 is a high level flow diagram depicting an Internet-basedvendor offer edit process in an exemplary embodiment of the presentinvention;

[0014]FIG. 12 is a high level flow diagram depicting an Internet-basedvendor offer delete process in an exemplary embodiment of the presentinvention;

[0015]FIG. 13 is a high level flow diagram depicting an Internet-basedvendor logo upload process in an exemplary embodiment of the presentinvention;

[0016]FIG. 14 is a high level flow diagram depicting an Internet-basedvendor logo delete process in an exemplary embodiment of the presentinvention;

[0017]FIG. 15 is a high level flow diagram depicting an Internet-basedvendor account update process in an exemplary embodiment of the presentinvention;

[0018]FIG. 16 is a high level flow diagram depicting an Internet-basedview vendor account transaction data process in an exemplary embodimentof the present invention;

[0019]FIG. 17 is a high level flow diagram depicting an Internet-basedvendor exit process in an exemplary embodiment of the present invention;

[0020]FIG. 18 is a high level flow diagram depicting a process in anexemplary embodiment of the present invention for transmitting a vendoroffer from the system through a vendor point of service terminal to acustomer handheld device;

[0021]FIG. 19 is a high level flow diagram depicting a process in anexemplary embodiment of the present invention for transmittingmicro-credits from a vendor's micro-credit account in the system througha vendor point of service terminal to a customer handheld device;

[0022] FIGS. 20-21 provide a high level flow diagram depicting a processin an exemplary embodiment of the present invention for a customer toredeem an approval-required vendor offer using a system-enabled customerhandheld device;

[0023]FIG. 22 is a high level flow diagram depicting a process in anexemplary embodiment of the present invention for a customer to redeeman no-approval-required vendor offer using a system-enabled customerhandheld device;

[0024] FIGS. 23-26 provide a high level flow diagram depicting a processin an exemplary embodiment of the present invention for a customer toaccess a vendor's offers using a wireless-enabled customer handhelddevice through a vendor doorway-location terminal;

[0025] FIGS. 27-30 provide a high level flow diagram depicting a processin an exemplary embodiment of the present invention for a customer toaccess a vendor's offers using a wireless-enabled customer handhelddevice through a wireless Internet connection to the system of thepresent invention; and

[0026]FIG. 31 is a high level simplified graphic representationdepicting high level software and data interfaces for customer access ofvendor offers using a wireless-enabled handheld customer device througha wireless-enabled billboard or kiosk in an exemplary embodiment of thepresent invention.

FACSIMILE REPRODUCTION OF COPYRIGHT MATERIAL

[0027] A portion of the disclosure of this patent document containsmaterial, which may be subject to copyright protection by Immtec, Inc.or other rightful copyright owner. Immtec, Inc., or other rightfulcopyright owner, has no objection to the facsimile reproduction byanyone of the patent document or the patent disclosure, as it appears inthe Patent and Trademark Office patent file or records, but otherwisereserves all copyright rights whatsoever.

[0028] Trademarks

[0029] Immtec™, Microwallet™, mewallet™, CSRA™, Customer SpecificReceipt Advertising™, and PayStick™ are trademarks of Immtec, Inc. Thenames of actual companies and products mentioned herein may be thetrademarks of their respective owners.

DETAILED DESCRIPTION OF THE INVENTION

[0030] In an exemplary embodiment present invention, a wireless handheld device would be used by a consumer to access and redeem vendoroffers. Wireless, hand held devices, include for example, wirelessPersonal Digital Assistants (“PDAs”), wireless telephones e.g., cellulartelephones, and wireless electronic authority and cash transfer devices,an exemplary embodiment of which is sometimes referred to as aPayStick™. In an exemplary embodiment of the present invention, thewireless hand held device would comprise a memory storage device forstoring data, an executable memory, a computer device, such as amicroprocessor, and short-range wireless communication hardware such asan infrared transceiver or Bluetooth radio transceiver, and relatedcommunication software and/or firmware. In some exemplary embodiments,the wireless hand held device would provide a display screen on whichinformation text, numbers and/or graphics can be displayed.

[0031] The CSRA Program

[0032] In an exemplary embodiment of the present invention, when a newcustomer establishes an account with Immtec™ for the mewallet™ system,they would be offered the CSRA service. If the new customer chooses tobe a part of this service, they would be asked a series of questionsregarding what areas of commerce in which they would like to be includedand the level of anonymity they would prefer. In the exemplaryembodiment of the invention, Microwallet™ credits (also sometimesreferred to herein as “coupons”) would be provided by service providersand retailers who choose to participate in the CSRA program. If amewallet™ customer chooses not to participate in the CSRA program, thentheir customer mewallet™ data would reflect this choice and they wouldnot receive advertising, offers or information based on their profile inthe Immtec™ database. They may receive printed receipt advertising, butthese advertisements or offers would not be generated based on thecustomer's data in the Immtec™ system. Customers would be able to, atany time, change their preferences for the CSRA program (also sometimesreferred to herein simply as the “system” or the “System”).

[0033] Signing up for the CSRA Program

[0034] Customer sign-up procedures for the CSRA program are describedbelow in an exemplary embodiment of the present invention and aredepicted in FIG. 1. In the exemplary embodiment of the presentinvention, the CSRA system would be operable to perform in the followingmanner:

[0035] Each customer would sign-up for the Immtec mewallet™ system onthe Internet or at a licensed service provider 101. Each Customer wouldbe given a user name and PIN, (Personal Identification Number) 102. Thecustomer would be offered a description of the CSRA service 103 andwould be given an opportunity to participate or not participate 104. Ifthe customer chooses not to participation in the CSRA program: theCustomer would check the ‘No’ option for the choice offered toparticipate in the CSRA program and a ‘No’ response would be noted incustomer's file in the Immtec database 105; and the Customer's datawould be stored but would not be accessible by the CSRA system or anyother service provider 106. (As previously noted, Customer data wouldnot be sold for any reason whatsoever).

[0036] If the customer chooses to participate 107 in the CSRA program:the customer would check ‘Yes’ for the choice offered to participate inthe CSRA program and a ‘Yes’ response is noted in the customer's file inthe Immtec database 108; and the system continues processing.

[0037] The Customer would then be offered a number of choices regardingareas of commerce in which the user could choose to participate or notparticipate (remain anonymous) 109. The Customer's choices of areas ofanonymity are recorded in the data corresponding to the particularCustomer in the Immtec database 110. Areas of anonymity chosen by eachcustomer are made inaccessible to the CSRA system 112. All other areasof a Customer's data are made accessible to the CSRA system 111.

[0038] At this point, the CSRA system would be ready for the particularCustomer's use 113.

[0039] Changing Data use Preferences

[0040] The process for a customer to change their data use preferencesettings, via the Internet, utilizing a personal computer orInternet-enabled mobile device, for the CSRA program is described belowin the exemplary embodiment and is depicted in FIG. 2.

[0041] In the exemplary embodiment of the present invention, in order tochange the Customer's data use preferences, a Customer would access theImmtec CSRA web site 201. The Customer would choose ‘Change my settings’202. The system screen would display a request for user name and PIN203.

[0042] The Customer would then enter the Customer's user name and PIN204 (In one alternative exemplary embodiment, abiometric-reader-interface-enabled-computer or mobile device would beprovided such that biometric data would replace the PIN).

[0043] The system sever would receive the user name and PIN and wouldcompare the received information with data in the customer database ofthe system 205-207. If on the first attempt, the user name and/or PINare incorrect 208, the Customer would be asked to input correct username and PIN 203. If user name and PIN are incorrect on the secondattempt, the Customer would be asked to call System customer service210.

[0044] If user name and PIN are correct 211, the System would display anOption screen and the Customer would be given an opportunity to updatethe Customer's options 212. If the Customer chooses to update options,the Customer could check or uncheck options 213 and could add textmessage to CSRA program 214. When the Customer's option updating iscomplete 215, the Customer could then click on an ‘Update’ button 219and updated use preference data is transmitted to Immtec's CSRA databasecenter. If a text message has been included in use updates, then the usepreference profile is updated by a Customer Service Representative(“CSR”) 216-217. If no text message is included in the update, thenupdated use preference data is transmitted to CSRA database, andCustomer's data use profile is updated by CSRA software 220. At thispoint, the Customer's data use profile would be updated 221.

[0045] The process for the customer to change their data use preferencesettings, via telephone, for the CSRA program is described below in theexemplary embodiment and is depicted in FIG. 3.

[0046] In the exemplary embodiment of the present invention, theCustomer would call Immtec CSRA customer service 301. The Customerchooses ‘Change my settings’ from the voice menu 302 and the Customerwould be connected to a Customer Service Representative (“CSR”) at theImmtec CSRA program center. The CSR would request the Customer's username and PIN 303. The CSR would input the user's name and PIN 304. Thesystem would receive the input name and PIN 305 and would check theaccuracy of the input 306-307. If the Customer's user name and PIN areincorrect, the CSR would request the user name and PIN again. If afterthe second try the name and PIN are incorrect, the CSR would requestpersonal information to see if it matches information in Immtec's database 309. If the personal information does not match 310, the Customer'srequest for access would be denied 311. If the personal informationmatches information in Immtec's database 312, then the CSR would inputthe correct user name and PIN so that the customer could continue withthe update process. Once the user name and PIN are correct 313, the CSRwould request the customer's desired changes 314. Once the Customergives the CSR the desired changes, the CSR would enter the changes tothe customer's data use profile 315. When the CSR has completed updatingthe Customer's options 316, the CSR would click on an “Update” icon 318.At that point, the system would update the customer's data in the CSRAdatabase 317 and the update would be complete 319.

[0047] The process for the customer to change their data use preferencesettings, at an authorized service center, for the CSRA program isdescribed below in the exemplary embodiment and as depicted in FIGS. 4,5, and 6. Note that in an alternative embodiment with a biometric readerinterface enabled computer at the Authorized service center, biometricdata would replace the PIN.

[0048] At an authorized service center, the Customer would requestchanges be made to their CSRA profile settings 401. The Service centerCSR would access a special Service Center Internet site 402. The ServiceCenter Internet site would request the service center's user ID 403. TheService center CSR would input user ID and would click ‘send’ 404. TheService center user ID is transmitted to the system's (e.g., Immtec'sCSRA) security middleware for accuracy checking 405-407.

[0049] If service center user ID is incorrect, the Service center CSRwould be instructed to input user ID a second time 408. If after a thirdattempt the ID is not correct, the CSR would be instructed to callImmtec customer service 409. If service center user ID is correct 410,the CSRA/Immtec service center site menu would be displayed 411. TheService center CSR could choose ‘Enter CSRA site’ 412. The CSRA systemsite menu for authorized service centers would be displayed 413. TheService center CSR would choose ‘Update customer data use profile’ 414.The CSRA system would request a user name of customer profile to change501. The Service center CSR would request that the customer input a username 502. The Customer would input the Customer's user name 503. TheCustomer would then click the ‘enter’ key on the keyboard 503. The Username would then be transmitted to Immtec 504.

[0050] The CSRA system would accesss the customer's data in the customerdatabase 505. The CSRA system would then request the customer's PIN orbiometric data 506. The Customer would then input PIN or biometric data507. The Customer would then click the ‘enter’ key on keyboard 507. TheCustomer's PIN would then be transmitted to the CSRA system 508. TheCSRA system would compare transmitted PIN with PIN in database 509.

[0051] If the PIN does not match the PIN in the CSRA database on thefirst attempt, the system would request that the data be re-input 511.If the PIN is not correct after the third attempt, the system wouldinstruct the Customer to contact customer service 512.

[0052] If user name and PIN are correct 513, the Customer's CSRA datause profile would be displayed 514.

[0053] The Service center CSR asks customer for desired changes toprofile 601 and the Customer would tell the service center CSR thechanges to make. The Service center CSR would input the desired changes602. The Service center CSR would then click the ‘update’ button on theCSRA site screen 603. The system would then update the customer's datause profile in the CSRA customer database 604-605, 608.

[0054] At that point, the system would end the session and would displayan opening menu 606 and no previous screens can be accessed by clickingon the browser's ‘back’ button. No data is written to the servicecenter's hard drive 607.

[0055] How the CSRA System Works

[0056] The CSRA system collects, compiles and collates all use,purchasing and spending data from each CSRA-enabled handheld customerdevice (e.g., “mewallet™”). This data is stored on secure system(“Immtec”) servers. When a customer conducts a transaction using amewallet™ device, the details of that transaction, including the amount,items purchased, method of payment used, date, time and location, aretransmitted to the Immtec CSRA system and stored in the customer's dataprofile. The customer chooses what data, if any, is incorporated intothe CSRA program. If the customer has chosen to participate in the CSRAprogram then the data that Immtec CSRA system collects is used to createa personalized use experience for the mewallet™ customer. Each time themewallet™ device is used for a transaction with a POS device that isconnected to the Immtec CSRA network via hardwire line or wireless, aprinted or electronic advertisement, coupon, offer or other information,specifically oriented to the customer and vendor, is generated by theCSRA system to the POS and added to the merchant's or service provider'sprinted or electronic receipt. The term ‘offer’ refers to any coupon,information, advertisement or message generated by the CSRA system andtransmitted for printing or transmission with a vendor receipt.

[0057] The CSRA system process as it would be implemented in theexemplary embodiment is described below and is depicted in FIGS. 7-8.

[0058] After customer has initiated mewallet™ transaction with a Vendor701, all details of transaction data are transmitted to Immtec/CSRAservers (alternatively referred to herein as “Immtec” servers) 702. Alldetails of transaction data are stored in customer's data file on Immtecservers 703.

[0059] The CSRA system recognizes each mewallet™ transaction in progress704. The CSRA system requests permission of the Immtec database foraccess to customer's data 705.

[0060] Immtec checks the customer's participation profile for the CSRAprogram 706-707. If the customer has chosen not to participate in CSRAprogram, the CSRA system is not granted access to the customer's data inthe Immtec database 708 and a generic offer, referencing the transactionvendor is transmitted for printing or electronic transmission with thereceipt 709.

[0061] If the customer has chosen to participate in the CSRA program710, the CSRA system is granted access to the customer's data 711. Atthat point, the CSRA system applies the customer's chosen filters to thetransaction data 712. The CSRA system searches for appropriate receiptoffer in the vendor's database 713. The CSRA system searches formicrowallet credit offers in the vendor's database 714. The CSRA systemlocates appropriate offer from vendor in the vendor's database at Immtec715. If available, the CSRA system locates appropriate Microwalletcredits from the vendor's Microwallet credit account at Immtec 716.

[0062] The CSRA system matches data from the customer profile withoffers in the vendor's database 717. The CSRA system generates an offerbased upon customer and Vendor/merchant profiles 718. The CSRA systemtransmits one or more appropriate offers through the vendor's system tothe vendor's receipt printer 801. If appropriate, the CSRA systemtransmits the appropriate Microwallet credit through the POS device tothe customer's handheld device via infrared or other wireless method808.

[0063] The mewallet™ software in the handheld device adds theMicrowallet credit to the Microwallet amount in memory of the handhelddevice 809-810. As the vendor's/merchant's receipt printer completesprinting, an appropriate receipt offer is added to the bottom of theprinted receipt 803. If the offer is transmitted to the vendor's POSterminal, the offer is added to electronic receipt transmitted to thecustomer's handheld device via infrared or other wireless method805-806.

[0064] Merchant Sign-up Process

[0065] A vendor could become a licensee of the CSRA program via theInternet at the Immtec web site, by calling the Immtec CSRA MerchantServices Center, by mailing in a CSRA licensee contract, or through aCSRA Merchant Services sales representative. A secure vendor accountwould include:

[0066] Vendor offers database

[0067] Microwallet credit offers account

[0068] Vendor data

[0069] Vendor logos in .bmp format

[0070] Access codes for updating vendor's data and uploading anddeleting offers at the Immtec CSRA secure web site

[0071] Access to general mewallet™ sales, offers and Microwallet creditstransmitted records, for vendor

[0072] Using the Vendor Immtec/CSRA Site

[0073] Using the features of the invention as it would be implemented inan exemplary embodiment, a vendor's offers can be created, deleted andedited at the Immtec/CSRA program offices and added to the vendor's CSRAdatabase as an add on service. Offers can also be created, edited,deleted and uploaded to the CSRA database by vendors at any time.Vendor's are provided with web-based software templates and training forcreating, editing, deleting and updating their offers. Vendor's cancross-market by creating alliance partnerships with other vendors.Offers from one vendor can be transmitted to receipts printed ortransmitted electronically, to that vendor's alliance partner(s). Anyoffer sent through alliance partners requires a signed agreement betweenall participating alliance partners filed at Immtec. Once a signedagreement is filed, Immtec issues the alliance partners unique agreementcodes for each offer. The offer uploaded must conform exactly to theagreement filed at Immtec.

[0074] Using the vendor Immtec/CSRA site process as it would beimplemented in an exemplary embodiment of the invention is describedbelow in the exemplary embodiment and is depicted in FIGS. 9-17.

[0075] 1. Entering the Vendor Immtec/CSRA Site

[0076] The entering vendor Immtec/CSRA site process as it would beimplemented in an exemplary embodiment is described below and isdepicted in FIG. 9.

[0077] A Vendor connects to Immtec/CSRA vendor login page on theInternet via computer system equipped with modem 901. On initial loginpage, Immtec requests vendor input username and password and click onthe send button on the page 902.

[0078] The Vendor inputs username and password and clicks on the sendbutton on the page 903. The Username and password are encrypted andtransmitted to Immtec 904. The Username and password are unencrypted andcompared with username and password in system database records 905-906.

[0079] The Vendor is given three attempts to input a correct usernameand password, 906-909. If after the third attempt, the input can not bevalidated, the Vendor is asked to call Immtec customer service 908.

[0080] If username and password are a correct match 909, the Vendorenters secure Immtec/CSRA vendor site 910. The CSRA vendor site menuscreen is displayed 911. The Menu items include 912: 1.) Upload newoffer; 2.) Edit offer; 3.) Delete offer; 4.) Upload logo; 5.) Deletelogo; 6.) Make changes to account; 7.) View Account Transactions; 8.)Exit the Immtec/CSRA system.

[0081] 2. Upload New Offer

[0082] If a vendor chooses to ‘Upload new offer’ 1002 (depicted in FIG.10 as the process would be implemented in an exemplary embodiment of theinvention), a ‘New Offer’ page appears 1003. The ‘New offer’ pagedisplays a template for a new offer 1005 which includes:

[0083] 1. Vendor name and information.(these fields are automaticallyfilled in but can be changed)

[0084] 2. Name of offer

[0085] 3. bmp file for offer to attach

[0086] 4. Description of offer as vendor wishes it to appear on receipt

[0087] 5. Choose font for offer

[0088] 6. Choose paragraph format for offer

[0089] 7. Offer begins: Date

[0090] 8. Offer ends: Date

[0091] 9. Merchandise or service code for offer

[0092] 10. Suggest new merchandise or service code

[0093] 11. Should this offer be offered to every customer? (Y/N)

[0094] 12. Should this offer be offered to customers who match CSRAprofile for the offer? (Y/N)

[0095] 13. Should this offer be offered to customers through one of youralliance partners? (Y/N)

[0096] 14. If you have answered yes, please input alliance agreementcode in the box below

[0097] 15. If you do not have a valid alliance agreement code, pleasecontact Immtec customer service

[0098] 16. Click on the ‘upload’ button when you have completed thisform

[0099] When vendor clicks on the ‘upload’ button all form data istransmitted to the the vendor's CSRA database 1006-1014, the Vendor'soffer database is updated 1015, and a message that “Your (name ofvender) offer has been added to your database” is transmitted to vendorvia Immtec/CSRA web site 1016.

[0100] 3. Edit Offer

[0101] If the vendor chooses ‘Edit offer’ 1102 (as depicted in FIG. 11as the process would be implemented in an exemplary embodiment of theinvention), an ‘Edit Offer’ page appears asking the Vendor which offerthey wish to edit 1103. The Vendor checks a box corresponding to theoffer that vendor want to edit and clicks on ‘send’ button to transmitname of offer to edit 1104.

[0102] The Immtec/CSRA system receives the edit request and displays forthe vendor a web page containing details about the offer 1105-1106,asking the Vendor to edit the offer data. Once the Vendor has edited theappropriate offer data, the Vendor clicks on an ‘Upload’ button 1108.The edited offer data is transmitted to the Immtec/CSRA system 1109-1114and the Vendor's CSRA database information is updated 1115. A messagethat “Your (name of vendor) offer has been updated in your database” istransmitted to the vendor via the Immtec/CSRA web site 1116.

[0103] 4. Delete Offer

[0104] If vendor chooses ‘Delete offer’ 1202 (as depicted in FIG. 12 asthe process would be implemented in an exemplary embodiment of theinvention), a ‘Delete offer’ web page is displayed requesting the vendorto input an identification of the offer to be deleted 1203. The Vendorfills in a box corresponding to a name of the offer to be deleted andclicks on a ‘Delete’ button to transmit name of offer to be deleted1204.

[0105] The Immtec/CSRA system receives the delete request, displays aweb page containing information about the offer to be deleted and asks,“Is this the offer you wish to delete?” (Y/N) 1205.

[0106] If the vendor clicks on ‘No’ 1206, the ‘Delete offer’ screen isdisplayed again and vendor can begin the process again 1203-1205. If thevendor clicks on ‘Yes’ 1207, then a pop up screen appears asking, “Areyou certain you would like to delete this (name) offer? (Y/N) 1208. Ifvendor clicks on ‘No’ 1206, the vendor is returned to ‘Delete offer’page 1203. If the vendor clicks on ‘Yes’ 1207, then a delete (name)offer is transmitted to Immtec/CSRA database 1209.

[0107] The Immtec/CSRA database receives the delete (name) offer command1210 and the Immtec/CSRA system deletes the identified offer from thevendor's offer records in the vendor database 1211. The Immtec/CSRAsystem transmits confirmation of the deletion 1212 that “Your (name)offer has been deleted from your database” to the vendor via theImmtec/CSRA web site 1212. At that point, the Immtec/CSRA main menu pageis displayed 1213.

[0108] 5. Upload Logo

[0109] If vendor chooses ‘Upload logo’ 1302 from main menu (as depictedin FIG. 13 as the process would be implemented in an exemplaryembodiment of the invention), an Upload logo dialog page is displayedprompting the vendor to click on a browse button 1303. If the vendorclicks on the browse button, the system searches the vendor'sinformation in the vendor's server storage memory to locate a logo .bmpfile corresponding to the vendor to upload 1304. If located, the .bmpfile corresponding to the vendor is chosen 1305, and is displayed on aweb page with the bitmap image of the vendor's logo 1306.

[0110] The Immtec/CSRA system prompts the vendor by asking “Is this thelogo you wish to upload to your database?” (Y/N) 1306. If the vendorresponds “No” 1307, the system restarts the Upload logo dialog pagedisplay and the process begins again 1303. If the vendor responds “Yes”1308, the system prompts the vendor with questions that are thendisplayed with boxes for answers 1309-1310, including:

[0111] 1. Would you like this logo attached to a particular offer? (Y/N)

[0112] 2. If yes, please type the name of the offer in this box

[0113] 3. Is there a time period for this logo to be printed receipts?(Y/N)

[0114] 4. If yes, please type time period in these boxes

[0115] 5. If no, this logo will be printed on receipts until you changeit or delete it.

[0116] The Vendor is then asked to click on the ‘Upload Logo’ button1311. The Vendor clicks on ‘Upload Logo’ button 1312. The .bmp file anddata are transmitted and added to Immtec/CSRA the vendor's database1313. The system then displays a message page that “Your logo upload hasbeen successful” to confirm the upload for the vendor 1314.

[0117] 6. Delete Logo

[0118] If the vendor chooses to ‘Delete Logo’ (as depicted in FIG. 14 asthe process would be implemented in an exemplary embodiment of theinvention) 1402:

[0119] a) a Delete logo page appears 1403.

[0120] b) All logos present in vendor's database appear on page withrequest: “Please click on logo(s) you would like to delete. Whenfinished, please click on the ‘Delete Logo’ button below” 1404.

[0121] c) When vendor has completed choosing, ‘Delete Logo’ button isclicked 1405.

[0122] d) Page appears with logo(s) chosen for deletion 1406.

[0123] e) Are you sure you wish to delete these logos? (Y/N) buttons1406.

[0124] f) If the vendor clicks on the ‘No’ button then initial DeleteLogo screen appears again 1407.

[0125] g) If the vendor clicks on the ‘Yes’ button then the delete orderis transmitted to the Immtec/CSRA vendor's database and logos aredeleted 1408-1410.

[0126] h) “Your delete order has been completed” page appears 1411.

[0127] i) Initial menu screen appears 1412.

[0128] 7. Making Changes to Account

[0129] If vendor chooses to ‘Make changes to your account’ option 1502(as depicted in FIG. 15 as the process would be implemented in anexemplary embodiment of the invention):

[0130] a) Account details page appears. 1503

[0131] b) All account details are in editable boxes. 1504

[0132] c) Vendor can edit any account detail except access codes oraccount number by typing in the edits on the web page. 1504

[0133] d) When editing is complete.

[0134] e) Vendor clicks on ‘Update Account’ button. 1505

[0135] f) New account data page is displayed. 1506

[0136] g) Vendor is asked on page, “Is all this account data correct?Please look it over before clicking on the Update button” (Y/N) buttons.1507

[0137] h) If vendor clicks on the ‘No’ button. 1508

[0138] i) The vendor account data editing page appears. 1506

[0139] j) If vendor clicks on the ‘Yes’ button: 1509

[0140] k) All data on account details page is transmitted to Immtec/CSRAvendor's database. All data is compared with previous account data. 1510

[0141] l) All data that does not match previous data overwrites previousdata. 1511-1512

[0142] m) Vendor's account data is updated. 1513

[0143] n) “Your account data has been successfully updated” pageappears. 1514

[0144] o) Immtec/CSRA main menu page appears. 1515

[0145] 8. View Account Transactions

[0146] If ‘View Account Transactions’ option is chosen 1602 (as depictedin FIG. 16 as the process would be implemented in an exemplaryembodiment of the invention):

[0147] a) Account transaction page is displayed. 1603

[0148] b) Transactions displayed include: 1604 Total customers usingmewallets, gross amount spent using mewallets, totals per product code,totals per location, total offers printed or transmitted, total offercoupons redeemed, total Microwallet credits transmitted, totalMicrowallet credits payed to Immtec, total Microwallet credits remainingin account.

[0149] c) At bottom of page is a ‘View historical totals’ button. 1605

[0150] d) If vendor clicks on ‘View historical totals’ button: 1606

[0151] e) Historical totals request page appears. 1607

[0152] f) ‘For what period would you like to see historical totals?Please fill in the dates in the boxes’ question is asked on page. 1607

[0153] g) Vendor fills in the appropriate dates in the boxes on the pageand clicks the ‘View’ button. 1608

[0154] h) Request for historical totals for vendor's account istransmitted to Immtec/CSRA database. 1609

[0155] i) Immtec/CSRA software compiles appropriate historical data forvendor's account. 1610

[0156] j) Immtec/CSRA transmits historical data to web page.

[0157] k) Historical data page appears with historical data forrequested dates. 1611

[0158] l) ‘Would you like to see historical totals from other dates?’Question is at bottom of page (Y/N). 1612

[0159] m) If vendor clicks on the ‘Yes’ button: 1613

[0160] n) Historical totals request page appears. 1607

[0161] o) If vendor clicks on the ‘No’ button: 1614

[0162] p) Main Immtec/CSRA menu page appears. 1615

[0163] 9. Exit the System

[0164] If vendor chooses ‘Exit the System’ option 1702 (as depicted inFIG. 17 as the process would be implemented in an exemplary embodimentof the invention):

[0165] a) ‘Thank you, (vendor's name), for using your update system andfor being a mewallet™ service provider’ page appears.

[0166] b) Vendor exits to Internet. 1703

[0167] Uploading Vendor Microwallet Credits

[0168] Each vendor has a Microwallet credit account from whichMicrowallet credits can be sent to customers as incentives and to Immtecas micropayments on transactions. In the exemplary embodiment of theinvention, each Vendor would ‘fill’ an account corresponding to thatVendor with an amount of money that the Immtec system, or in thealternative, Immtec system representatives, would calculate to be anapproximate amount for 30 days of Microwallet credits. If credits reacha level below an agreed upon amount, Immtec would bill the vendor theamount necessary to ‘fill’ the Microwallet credit account to theagreed-upon amount. Vendor Microwallet credits would be uploaded byImmtec to the vendor's account when Immtec receives payment for theamount needed to ‘fill’ the vendor's Microwallet™ credit account.

[0169] When the vendor and Immtec establish a Microwallet™ creditaccount, certain parameters would be established, including, forexample:

[0170] a) How much money is kept in the Microwallet credit account.

[0171] b) What is the minimum amount of money needed in the Microwalletcredit account.

[0172] c) Form of payment to Immtec for the Microwallet credit account.

[0173] d) Distribution of Microwallet credits to customers:

[0174] 1. How many per amount customer spends

[0175] 2. Special incentive offers

[0176] 3. Time frames for special incentive offers

[0177] 4. Offers involving vendor's alliance partners

[0178] e) Percentage of micropayments to Immtec for mewallet™ sales.

[0179] Transmitting Offer to POS Printer

[0180] When a customer makes a payment for a purchase or service througha POS device, the credit card, bank account or debit card data istransmitted to a clearinghouse for approval. If the customer is using anImmtec mewallet™ enabled device for the transaction, the following datawould also be transmitted to the Immtec database:

[0181] 1. Security & identity data for approval

[0182] 2. Ticket redemption data for approval

[0183] 3. Purchase data

[0184] 4. Location data

[0185] 5. vendor data

[0186] 6. Microwallet level data

[0187] 7. micropayment from Microwallet

[0188] The process for transmitting a vendor's offer through the POSdevice to the vendor's receipt printer is described below as would beimplemented in the exemplary embodiment and as is depicted in FIG. 18:

[0189] a) Immtec server receives transaction data from POS terminal atvendor's location. 1801

[0190] b) During approval process, Immtec software checks customerprofile for inclusion in the CSRA program. 1802

[0191] c) If Immtec software detects a ‘No’ answer to customer'sinclusion in the CSRA program: 1803

[0192] d) Then appropriate approval or denial is transmitted to POSterminal without any customer specific advertising. 1804

[0193] e) A generic ad from vendor's database is transmitted forprinting with customer's receipt from vendor's receipt printing device.1805,1812-1818

[0194] f) If Immtec software detects a ‘Yes’ answer to customer'sinclusion in the CSRA program: 1806

[0195] g) Immtec is granted access to customer's profile in the CSRAdatabase. 1807

[0196] h) Immtec adds present location, time and all purchase data tocustomer's CSRA database file. 1808

[0197] i) Immtec compares present location, time and all purchase datawith personal preference data in customer's database and offer data invendor's database. 1809

[0198] j) Immtec/CSRA software matches a vendor or alliance partneroffer to customer's personal preferences. 1810

[0199] k) Immtec/CSRA transmits approval/disapproval as well as offerfrom vendor's database attached to receipt through vendor's POSterminal. 1811

[0200] l) Vendor's offer print's on customer's printed receipt fromvendor's receipt printer. 1812

[0201] m) and/or

[0202] n) Immtec/CSRA transmits offer is transmitted from vendor'sdatabase through vendor's POS device to customer's handheld via infraredor other wireless method. 1813

[0203] o) Receipt and offer appear on customer's handheld screen. 1814

[0204] p) Customer can choose to save receipt and offer or delete them.

[0205] q) If customer chooses to delete receipt/offer: 1816

[0206] r) Customer presses the ‘delete’ button or icon on handheld.

[0207] s) Receipt/offer is deleted from memory. 1819

[0208] t) If customer chooses to ‘save’ receipt/offer: 1815

[0209] u) Customer presses the ‘save’ button or icon. 1817

[0210] v) Receipt/offer is saved in mewallet™ in handheld's memory. 1818

[0211] Transmitting Micropayment Credits from Vendor's MicrowalletCredit Account

[0212] Microwallet micropayment credits are electronic money creditsthat would be saved in the vendor's Microwallet credit account on theImmtec/CSRA servers. Funds for the vendor's Microwallet credit accountwould be save in Immtec's bank account. Microwallet micropayment creditswould be transmitted to the vendor's customers during mewallet™transactions according to the parameters established by the vendor.Customer must be signed-up for the CSRA program to receive Microwalletmicropayment credits.

[0213] The process for transmitting a vendor's Microwallet micropaymentcredit through the POS device to the customer's handheld device as theprocess would be implemented in the exemplary embodiment of theinvention is described below and is depicted in FIG. 19:

[0214] a) Mewallet™ transaction data is transmitted via infrared orother wireless method through vendor's POS device to clearinghouse andImmtec. 1901

[0215] b) Immtec compares transaction data with Microwallet micropaymentcredit offers in location's (vendor's) database. 1902

[0216] c) If Microwallet micropayment credit offer does not matchestransaction data. 1903

[0217] d) No micropayment credit is transmitted. 1904

[0218] e) If Microwallet micropayment credit offer matches transactiondata. 1905

[0219] f) Microwallet micropayment credit is transmitted with vendor'sreceipt/offer through vendor's POS device to customer's handheld viainfrared or other wireless method. 1906

[0220] g) Customer receives Microwallet micropayment credit in handheldvia infrared or other wireless method. 1907

[0221] h) Message appears on screen of handheld, “A Microwalletmicropayment credit of has been deposited in your mewallet™ Microwalletcourtesy of (name) vendor”. 1908

[0222] i) Microwallet micropayment credit is received into thecustomer's mewallet™ Microwallet.

[0223] j) Microwallet micropayment credit is added to customer'smewallet™ Microwallet total and ready for use. 1909

[0224] Redeeming Vendor's Offers by Customer Using Mewallet™ EnabledHandheld for Offers Requiring Approval

[0225] An offer printed on the customer's receipt would be redeemed in amanner similar to the way in which a traditional hardcopy paper couponoffer is redeemed with a vendor. An offer held electronically in themewallet in the handheld device would be redeemed electronically at thevendor's location whether in a physical location or an Internetlocation. Some offers will require approval to be redeemed as prescribedby offering vendor. Some offers will not require approval.

[0226] The process for electronically redeeming a vendor's offer thatrequires approval, from the customer's handheld device, as the processwould be implemented in the exemplary embodiment of the invention isdescribed below and is depicted in FIGS. 20-21:

[0227] a) Customer accesses the mewallet™ software in their handhelddevice. 2001

[0228] b) Main menu appears after security protocols are passed. 2002

[0229] c) Customer chooses ‘use coupon’ menu choice. 2003

[0230] d) List of offers appear on screen of handheld, (customer canscroll down/up to see all choices). 2004

[0231] e) Customer scrolls to appropriate coupon/offer. 2005

[0232] f) With coupon/offer chosen on screen customer presses ‘send’icon or button. 2006-2007

[0233] g) Electronically held offer is transmitted with customer'sunique, encrypted security code and identification data to vendor's POSterminal via IrDA or other local wireless method. 2008

[0234] h) Customer's electronically transmitted offer and uniqueencrypted security code and identification data are transmitted throughvendor's POS terminal to Immtec/CSRA database.

[0235] i) Immtec software compares customer's identification data withrecords in database. 2010

[0236] j) If customer's identification data does not match and isincorrect: 2011

[0237] k) Immtec sends request for customer to resend electronic offerthrough vendor's POS terminal to customer's handheld. 2012

[0238] l) Customer sees resend on screen of handheld and presses ‘send’button or icon. 2013

[0239] m) Customer's electronically transmitted offer and uniqueencrypted security code and identification data are transmitted throughvendor's POS terminal to Immtec/CSRA database. 2008

[0240] n) Immtec software compares customer's identification data withrecords in database. 2010

[0241] o) If customer's identification data does not match and isincorrect: 2011

[0242] p) Immtec transmits local customer service number to customer'shandheld via vendor's POS terminal with request to call. 2014

[0243] q) Offer cannot be used without approval from Immtec. 2015

[0244] r) If customer's identification data is correct: 2101

[0245] s) Immtec software checks vendor's database to check on validityand parameters of offer, (time, location, if offer is in vendor'sdatabase). 2102

[0246] t) If offer is not a valid offer or time has expired: 2103

[0247] u) Invalidity is transmitted to customer's handheld device viavendor's POS terminal. 2104

[0248] v) If offer is valid: 2105

[0249] w) Redemption of vendor offer is recorded in Immtec's database.2106

[0250] x) Approval for electronic offer is transmitted to vendor via POSterminal. 2107

[0251] y) Redemption of offer is completed on vendor's POS terminal.2108

[0252] z) Delete offer is transmitted to customer's handheld terminalvia network from Immtec. 2019

[0253] aa) mewallet™ software deletes offer in customer's handheldterminal. 2110

[0254] Redeeming Vendor's Offers by Customer Using Mewallet™ EnabledHandheld for Offers not Requiring Approval

[0255] Some vendor offers do not require approval. For suchno-approval-required offers, the process for electronically redeeming avendor's offer from the customer's handheld device is described below asthe process would be implemented in the exemplary embodiment of theinvention and is depicted in FIG. 22:

[0256] a) Customer accesses the mewallet™ software in their handheldterminal. 2201

[0257] b) Main menu appears after security protocols are passed. 2202

[0258] c) Customer chooses ‘use coupon’ menu choice. 2203

[0259] d) List of coupons appear on screen of handheld, (customer canscroll down/up to see all choices). 2204

[0260] e) Customer scrolls to appropriate coupon/offer. 2205

[0261] f) With coupon/offer chosen on screen customer presses ‘send’icon or button. 2206-2207

[0262] g) Electronically held offer is transmitted with customer'sunique, encrypted security code and identification data to vendor's POSterminal via IrDA or other local wireless method. 2208

[0263] h) Customer's electronically transmitted offer and uniqueencrypted security code and identification data are transmitted throughvendor's POS terminal to Immtec/CSRA database. 2209

[0264] i) Immtec software checks vendor's database to check on validityand parameters of offer, (time, location, if offer is in vendor'sdatabase). 2210

[0265] j) If offer is not valid or time has expired: 2211

[0266] k) Invalidity of offer is transmitted to customer's handhelddevice via vendor's POS terminal. 2212

[0267] l) If offer is valid: 2213

[0268] m) Redemption of vendor offer is recorded in Immtec's database.2214

[0269] n) Approval for electronic offer is transmitted to vendor via POSterminal. 2215

[0270] o) Redemption of offer is completed on vendor's POS terminal.2216

[0271] p) Delete offer is transmitted to customer's handheld terminalvia network from Immtec. 2217

[0272] q) mewallet™ software deletes offer in customer's handheldterminal. 2218

[0273] Mewallet™ Customer Accesses Vendor Offer Database upon EnteringVendor's Location via IrDA or Other Wireless Method.

[0274] A doorway feature would be implemented in the exemplaryembodiment of the invention such that when a customer who has signed upfor CSRA program enters a vendor's location, the customer has the optionof focusing an IrDA or other wireless transceiver on their handheldterminal at a transceiver at a portal in the vendor's location. Afterestablishing communication between the two transceivers, the customercould download all vendor offers that are applicable to the customer'sprofile and date of entering the vendor's location. This vendor offerdata could also be downloaded into the customer's handheld terminal viawireless Internet communication if the handheld terminal is wirelessInternet capable. In the exemplary embodiment, ‘store’ refers to anyvendor location. The process of downloading vendor offers and redeemingthose offers at a vendor's store portal is described below as theprocess would be implemented in the exemplary embodiment and is depictedin FIGS. 23-26.

[0275] a) Customer enters doorway of vendor's location. 2301

[0276] b) Customer points IrDA or other wireless transceiver towardstransceiver located in portal to vendor's store. 2302

[0277] c) Customer opens mewallet™ software program on handheld device.2303

[0278] d) Customer chooses ‘Download new merchant offers’ from openingmenu. 2304

[0279] e) mewallet™ software in handheld device transmits request forappropriate vendor offers to Immtec/CSRA system via IrDA or otherwireless method through communication port at vendor's location. 2305

[0280] f) The mewallet™'s transmission includes the customer's uniqueencrypted security code. Immtec accesses customer's encrypted CSRAdatabase and security data. 2307

[0281] g) The Immtec/CSRA system receives customer's request forappropriate vendor offers. 2306

[0282] h) Immtec transmits request for customer's password or biometricdata. 2401

[0283] i) Request for security data is displayed on screen of customer'shandheld device. 2402

[0284] j) Customer inputs password or biometric data. 2403

[0285] k) Customer transmits data to Immtec by pressing on the ‘send’button or icon. 2404

[0286] l) Security data is transmitted to Immtec's server via wirelessconnection through network. 2405

[0287] m) Immtec server software compares transmitted security data withpassword or biometric data in customer's database. 2406

[0288] n) If security data does not match. 2407

[0289] o) Immtec transmits request for customer's password or biometricdata. 2401

[0290] p) A second request for security data is displayed on screen ofcustomer's handheld device. 2402

[0291] q) Customer inputs password or biometric data. 2403

[0292] r) Customer transmits data to Immtec by pressing on the ‘send’button or icon. 2404

[0293] s) Security data is transmitted to Immtec's server via wirelessconnection through Immtec's Internet portal. 2405

[0294] t) Immtec server software compares transmitted security data withpassword or biometric data in customer's database. 2406

[0295] u) If security data does not match: 2407

[0296] v) A third request is transmitted for security data to customer'shandheld device.

[0297] w) If on the third attempt the security data is incorrect:

[0298] x) Immtec transmits request for customer to call Immtec customerservice. 2408

[0299] y) Request for customer to call Immtec customer service isdisplayed on screen of handheld device.

[0300] z) If security data is correct. 2409

[0301] aa) The Immtec/CSRA system accesses customer's encrypted profiledata. 2501

[0302] bb) The Immtec/CSRA system accesses vendor's present offers invendor's CSRA database. 2502

[0303] cc) The Immtec/CSRA system matches all present vendor offers withcustomer's profile data. 2503

[0304] dd) All offers that match customer's profile data are transmittedthrough the communication port at vendor's location portal to customer'shandheld device via IrDA or other wireless method. 2504

[0305] ee) All appropriate vendor offers appear as a list on screen ofcustomer's handheld terminal. 2505

[0306] ff) Customer scrolls up or down to view vendor offers by pressingon the scroll button on the handheld terminal. 2506

[0307] gg) User has 4 menu options that appear on handheld terminalscreen: 2507

[0308] 1. Save all offers in your mewallet™

[0309] 2. Delete all offers

[0310] 3. Choose offer to save in your mewallet™

[0311] 4. Choose offer to delete

[0312] hh) If customer chooses 1: 2601

[0313] ii) All downloaded offers are written into the mewallet™ memoryand stored. 2602

[0314] jj) If customer chooses 2: 2603

[0315] kk) All downloaded offers are deleted from the mewallet™ RAM.2604

[0316] ll) If customer chooses 3: 2605

[0317] mm) Customer scrolls through vendor offers and highlights onethen clicks or pushes on the appropriate button or icon for ‘save’. 2606

[0318] nn) Chosen offer is then written into the mewallet™ memory andstored. 2607

[0319] oo) If customer chooses 4: 2608

[0320] pp) Customer scrolls through vendor offers and highlights onethen clicks or pushes on the appropriate button or icon for ‘delete’.2609

[0321] qq) Vendor offer is then deleted from the mewallet™ RAM. 2610

[0322] Mewallet™ Customer Accesses Vendor Offer Database via WirelessInternet Capable Handheld Device.

[0323] A wireless vendor offer access feature would be implemented inthe exemplary embodiment of the invention such that the mewallet™ systemin a handheld terminal would be capable of downloading and storingvendor offers from the Internet utilizing any wireless Internet protocolthrough which the handheld terminal is capable of wireless Internetconnectivity. The process for downloading and redeeming vendor offersfrom the Internet with the mewallet™ system is described below as itwould be implemented in the exemplary embodiment and is depicted inFIGS. 27-30.

[0324] a) Customer opens mewallet software program on handheld device.2701

[0325] b) Customer connects to Immtec's wireless Internet portal viahandheld device. 2702

[0326] c) Customer's mewallet™ unique encrypted security code istransmitted simultaneously. 2703

[0327] d) Immtec server accesses customer's CSRA database and securitydata. 2704

[0328] e) Immtec transmits request for customer's password or biometricdata. 2801

[0329] f) Request for security data is displayed on screen of customer'shandheld device. 2802

[0330] g) Customer inputs password or biometric data. 2803

[0331] h) Customer transmits data to Immtec by pressing on the ‘send’button or icon. 2804

[0332] i) Security data is transmitted to Immtec's server via wirelessconnection through Immtec's Internet portal. 2805

[0333] j) Immtec server software compares transmitted security data withpassword or biometric data in customer's database. 2806

[0334] k) If security data does not match. 2807

[0335] l) Immtec transmits request for customer's password or biometricdata. 2801

[0336] m) A second request for security data is displayed on screen ofcustomer's handheld device. 2802

[0337] n) Customer inputs password or biometric data. 2803

[0338] o) Customer transmits data to Immtec by pressing on the ‘send’button or icon. 2804

[0339] p) Security data is transmitted to Immtec's server via wirelessconnection through Immtec's Internet portal. 2805

[0340] q) Immtec server software compares transmitted security data withpassword or biometric data in customer's database. 2806

[0341] r) If security data does not match: 2807

[0342] s) A third request is transmitted for security data to customer'shandheld device. 2801

[0343] t) If on the third attempt the security data is incorrect:

[0344] u) Immtec transmits request for customer to call Immtec customerservice. 2808

[0345] v) Request for customer to call Immtec customer service isdisplayed on screen of handheld device. 2809

[0346] w) If security data is correct: 2810

[0347] x) Immtec's wireless Internet portal menu is displayed on screenof handheld device. 2901

[0348] y) Customer scrolls to menu option; ‘Download Merchant offers’then clicks on ‘send’. 2902

[0349] z) ‘Download Merchant offers’ request is transmitted toImmtec/CSRA server via wireless Internet portal. 2903

[0350] aa) New menu is transmitted to customer's handheld and appears onscreen.

[0351] bb) “Please say or type in the merchant name you would like todownload offers for”, appears on customer's handheld screen.

[0352] cc) If customer's handheld device supports audio transmissionthen customer can say the name of the merchant.

[0353] dd) The audio data is transmitted to the Immtec/CSRA server'svocal recognition system and translated into binary data and transmittedto the Immtec/CSRA system. 2904

[0354] ee) If customer types in the merchant name and presses ‘send’.

[0355] ff) Merchant name is transmitted to Immtec/CSRA system. 2904

[0356] gg) Immtec/CSRA system matches customer's preference data withchosen vendor offers. 2907

[0357] hh) Filtered offers are transmitted via Immtec/CSRA wirelessInternet portal to customer's handheld device. 2908

[0358] ii) Merchant offers appear on screen of user's handheld device.2909

[0359] jj) Customer scrolls up or down to view vendor offers by pressingon the scroll button of the handheld terminal. 2910

[0360] kk) Customer also has 4 options that appear: 2911

[0361] 1. Save all offers in your mewallet™

[0362] 2. Delete all offers

[0363] 3. Choose offer to save in your mewallet™

[0364] 4. Choose offer to delete

[0365] ll) If customer chooses 1: 3001

[0366] mm) All downloaded offers are written into the mewallet™ memoryand stored. 3002

[0367] nn) If customer chooses 2: 3003

[0368] oo) All downloaded offers are deleted from the mewallet™ RAM.3004

[0369] pp) If customer chooses 3: 3005

[0370] qq) Customer scrolls through vendor offers and highlights onethen clicks or pushes on the appropriate button or icon for ‘save’. 3006

[0371] rr) Chosen offer is then written into the mewallet™ memory andstored. 3007

[0372] ss) If customer chooses 4: 3008

[0373] tt) Customer scrolls through vendor offers and highlights onethen clicks or pushes on the appropriate button or icon for ‘delete’.3009

[0374] uu) Vendor offer is then deleted from the mewallet™ RAM. 3010

[0375] vv) Appropriate offers are now ready for redemption.

[0376] ww) Customer can then end wireless Internet connection withImmtec's wireless Internet portal or choose another menu item from themain menu. 3011

[0377] Mewallet™ Customer Accesses Vendor Offer Database at anInteractive Billboard, Kiosk or Other out of Home Advertising Medium viaIrDA or Other Wireless Method.

[0378] An interactive billboard/kiosk feature would be implemented inthe exemplary embodiment of the invention such that when a customer whohas signed up for CSRA program passes by a billboard, kiosk or otherout-of-home advertising medium equipped with a local wireless interfacesuch as IrDA or short range radio transceiver, the customer would havethe option of focusing the IrDA or other wireless transceiver on theirhandheld terminal at a transceiver at the local wireless equippedbillboard, kiosk or other out-of-home advertising medium. Afterestablishing communication between the two transceivers, the customerwould download all vendor offers (including Microwallet™ credits), whichare applicable to the customer's profile and date of offers. In theexemplary embodiment, ‘store’ refers to any vendor location and“billboard”/“kiosk” refers to any out of home advertising medium. (Thesecurity data request procedure is optional.) The process of downloadingvendor offers from a billboard/kiosk is described below as the processwould be implemented in the exemplary embodiment and is the same as isdepicted in FIGS. 23-26, and 28 except for the difference in location ofthe short-range wireless interface (reference is also made to FIG. 31).(Billboard/kiosk rather than vendor portal.):

[0379] a) Customer stops at billboard/kiosk. 3119,2301

[0380] b) Customer points IrDA or other wireless transceiver 3120towards transceiver located in billboard/kiosk 3119.

[0381] c) Customer opens mewallet™ software program 3125 on handhelddevice.

[0382] d) Customer chooses ‘Download new merchant offers’ from openingmenu.

[0383] e) mewallet™ software 3125,3123 in handheld device transmitsrequest for appropriate vendor offers to Immtec/CSRA system 3112, 3100via IrDA or other wireless method through communication port atbillboard/kiosk 3119.

[0384] f) The mewallet™'s transmission includes the customer's uniqueencrypted security code. Immtec accesses customer's encrypted CSRAdatabase 3100-3102, 3104 and security data 3114,3116.

[0385] g) The Immtec/CSRA system receives customer's request forappropriate vendor offers 3118.

[0386] h) Immtec transmits request for customer's password or biometricdata 3116,3118.

[0387] i) Request for security data is displayed on screen of customer'shandheld device.

[0388] j) Customer inputs password or biometric data.

[0389] k) Customer transmits data to Immtec by pressing on the ‘send’button or icon.

[0390] l) Security data is transmitted to Immtec's server via wirelessconnection through network. 2405, 3118, 3116.

[0391] m) Immtec server software compares transmitted security data withpassword or biometric data in customer's database 3116, 3114.

[0392] n) If security data does not match.

[0393] o) Immtec transmits request for customer's password or biometricdata.

[0394] p) A second request for security data is displayed on screen ofcustomer's handheld device.

[0395] q) Customer inputs password or biometric data.

[0396] r) Customer transmits data to Immtec by pressing on the ‘send’button or icon.

[0397] s) Security data is transmitted to Immtec's server via wirelessconnection through Immtec's Internet portal.

[0398] t) Immtec server software compares transmitted security data withpassword or biometric data in customer's database.

[0399] u) If security data does not match:

[0400] v) A third request is transmitted for security data to customer'shandheld device.

[0401] w) If on the third attempt the security data is incorrect:

[0402] x) Immtec transmits request for customer to call Immtec customerservice.

[0403] y) Request for customer to call Immtec customer service isdisplayed on screen of handheld device.

[0404] z) If security data is correct.

[0405] aa) The Immtec/CSRA system accesses customer's encrypted profiledata 3104, 3114,3100,3101.

[0406] bb) The Immtec/CSRA system accesses vendor's present offers invendor's CSRA database 3115,3102,3104.

[0407] cc) The Immtec/CSRA system matches all present vendor offers withcustomer's profile data, 3101-3102.

[0408] 1. All offers are transmitted from Immtec/CSRA/Microwallet™servers to communication port in billboard/kiosk, 3111,3104,3118

[0409] dd) All offers that match customer's profile data are transmittedthrough the communication port in billboard/kiosk to customer's handhelddevice via IrDA or other wireless method. 2504, 3119, 3120, 3124, 3122,3123

[0410] ee) All appropriate vendor offers appear as a list on screen ofcustomer's handheld terminal. 2505, 3125

[0411] ff) Customer scrolls up or down to view vendor offers by pressingon the scroll button on the handheld terminal. 2506, 3121

[0412] gg) User has 4 menu options that appear on handheld terminalscreen: 2507, 3125

[0413] 1. Save all offers in your mewallet™

[0414] 2. Delete all offers

[0415] 3. Choose offer to save in your mewallet™

[0416] 4. Choose offer to delete

[0417] hh) If customer chooses 1: 2601

[0418] ii) All downloaded offers are written into the mewallet™ memoryand stored. 2602

[0419] jj) If customer chooses 2: 2603

[0420] kk) All downloaded offers are deleted from the mewallet™ RAM.2604

[0421] ll) If customer chooses 3: 2605

[0422] mm) Customer scrolls through vendor offers and highlights onethen clicks or pushes on the appropriate button or icon for ‘save’. 2606

[0423] nn) Chosen offer is then written into the mewallet™ memory andstored. 2607

[0424] oo) If customer chooses 4: 2608

[0425] pp) Customer scrolls through vendor offers and highlights onethen clicks or pushes on the appropriate button or icon for ‘delete’.2609

[0426] qq) Vendor offer is then deleted from the mewallet™ RAM. 2610,3121, 3125

[0427] Illustrative Embodiments

[0428] Although this invention has been described in certain specificembodiments, many additional modifications and variations would beapparent to those skilled in the art. For example, reference herein tothe “Immtec” system and to “Immtec” servers are exemplary references toa system for processing the information and for performing the functionsherein described and to server computers on which such a system isoperable; such references are not a limitation of the invention. It is,therefore, to be understood that this invention may be practicedotherwise than as specifically described. Thus, the embodiments of theinvention described herein should be considered in all respects asillustrative and not restrictive, the scope of the invention to bedetermined by the appended claims and their equivalents rather than theforegoing description.

What is claimed is:
 1. A computer-implemented method for providingcustomer specific receipt promotional offers, said method comprising:storing customer-specific preferences for each participating customer ina database; correlating vendor-specified promotional offers for aparticular vendor to a particular participating customer'scustomer-specific preferences; and communicating one or morevendor-specified promotional offers for the particular vendor to theparticular participating customer.
 2. The computer-implemented method ofclaim 1, wherein said communication is performed in response to theparticular participating customer making a purchase from the particularvendor.
 3. The computer-implemented method of claim 1, wherein saidcommunication is performed in response to the particular participatingcustomer using a hand-held wireless device to communicate a request foravailable promotional offers.
 4. The computer-implemented method ofclaim 1, wherein said communication is a printed promotional offer. 5.The computer-implemented method of claim 1, wherein said communicationis a transmission of an electronically redeemable promotional offer to ahand held device of the particular participating customer.
 6. A wirelesshand held device for storing an electronically redeemable promotionaloffer, said device comprising: an executable program for receiving anelectronically redeemable promotional offer; and an executable programfor storing said electronically redeemable promotional offer in a memorystorage device in said wireless hand held device.
 7. A wireless handheld device for storing an electronically redeemable promotional offer,said device comprising: a memory storage device for storing data; anexecutable memory; a microprocessor; short-range wireless communicationhardware; program instructions to support short-range wirelesscommunication; an executable program for receiving an electronicallyredeemable promotional offer; and an executable program for storing saidelectronically redeemable promotional offer in a memory storage devicein said wireless hand held device.
 8. A computer-implemented method forstoring an electronically redeemable promotional offer, said methodcomprising: receiving an electronically redeemable promotional offer;and storing said electronically redeemable promotional offer in a memorystorage device in said wireless hand held device.